Skip to content

NullPointerException in reactor-netty SniProvider when SSL bundle uses client-auth or server truststore without server-name-bundles#50301

Open
kwondh5217 wants to merge 1 commit into
spring-projects:3.5.xfrom
kwondh5217:fix/50246-sni-fallback
Open

NullPointerException in reactor-netty SniProvider when SSL bundle uses client-auth or server truststore without server-name-bundles#50301
kwondh5217 wants to merge 1 commit into
spring-projects:3.5.xfrom
kwondh5217:fix/50246-sni-fallback

Conversation

@kwondh5217
Copy link
Copy Markdown
Contributor

@kwondh5217 kwondh5217 commented May 6, 2026

Falls back to the default SslProvider when the SNI hostname is not
present in server-name-bundles. The lookup logic is extracted into
a package-private getSslProvider(String) method to make it directly
testable.

A unit test is used instead of an end-to-end test because the
synchronous SNI lookup exception is silently swallowed inside Netty's
SslClientHelloHandler and the handshake falls back to the default
SslContext, so the NPE does not surface at the response level
(see netty/netty#16794).

Closes gh-50246

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label May 6, 2026
@kwondh5217 kwondh5217 force-pushed the fix/50246-sni-fallback branch from 5519425 to 5e0d655 Compare May 6, 2026 17:05
@kwondh5217 kwondh5217 changed the title Fall back to default SSL provider for unmapped SNI hostnames NullPointerException in reactor-netty SniProvider when SSL bundle uses client-auth or server truststore without server-name-bundles May 6, 2026
Signed-off-by: Daeho Kwon <trewq231@naver.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: bug A general bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants